home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Utilities Professional 1-1500
/
Utilities Professional 1-1500 (1994)(WPD)[!].iso
/
12511500
/
var1404.dms
/
var1404.adf
/
UPDATE.DOC
< prev
next >
Wrap
Text File
|
1994-04-17
|
18KB
|
581 lines
Device-Masher System Version 2.03
BUGS&UPDATES REPORT DOCUMENTATION
Chapter Name
----------------------------------------------------------------------
1. ..............................Bulletin Board Information
2. ..............................News in dms
1. ................................DMS.DEVICE
2. ................................SFXDMS
3. ................................UNDMS
4. ................................DMSWB
5. ................................FMS
3. ..............................Update/Bug Report v2.03
1. ................................v2.02
2. ................................v2.01
3. ................................v2.00
4. ................................v1.53
5. ................................v1.52
4. ..............................Register information
5. ..............................Bulletin Board Support
Chapter 1.
----------
FOR BBS OWNERS ... Only for users of /X 2.x/3.x or clones
Included with this archive you can find a new DMS checker utility
made to support the new standards, Highdensity files, etc...
(REWRITTEN LAYOUT ,MORE INFORMATIVE, AND FASTER!!!! V1.32)
IT IS HIGHLY RECOMMENDED THAT YOU USE THE "DMSTEST" PROGRAM, AS
THE WELLKNOWN "MAPUS" DESTROYS THE HEADERINFO(PARTLY), AND
WILL IN NEAR FUTURE RESULT IN DMS SHOWING INCORRECT INFORMATION
AND COULD UNPACK YOUR FILE INCORRECTLY.
OR THE DEVELOPER OF "Mapus" COULD MAKE AN UPDATE, WHICH FOLLOWS
THE RESTRICTIONS TOLD/SHOWN IN THE "DEVELOPER" SECTION.
Chapter 2.
----------
NEWS IN DMS .
-------------
Following is an explanation of new features since dms v2.x.
2.1. DMSDEVICE
---------
The device driver which can be found in the DEVS: directory on this
disk is for the mounting of a virtual drive. But not as you normally
would expect. Unlike FFx: FMx: , DMS-DEVICE is for mounting DMS files,
and accessing files included in the archive without having to extract it.
So the main difference between FMx/FFx and our DMx: device, is that
FMS.device and FFx.device takes up 901120 bytes pr. disk, And DMS.device
only uses the same space which your DMS file does.
2.2. SFXDMS
------
SFXDMS is a part of DMS, which gives you the option of creating
executable DMS files, which can be extracted without the need of
the DMS program.
The executable file will only occupy memory for the main program.
Data will be loaded in one track at a time, and depacked.
The new option in DMS for this, is SFX.
Read more about this later in this documentation.
ADVANTAGE:
*SIMPLE PATCH FILES WHICH WILL UNPACK WITHOUT NEED OF DMS.
2.3. UNdms
-----
UNdms can only unpack DMS files.
The main reason for making this tool is for those who need to
include DMS archives on their disk.
But because of the minimizing of the filesize, boottracks will not
be tested for viruses nor shown.
UNdms works with all the supplied options as in the FULL DMS.
but unlike DMS, UNdms will not use verification of data written to
disk as default. you must use the "VERIFY" option for verification.
ADVANTAGES:
*MORE SPACE ON THE DISKS WHERE DMS, IS A PART OF THE TOOLS
WHICH IS NEEDED TO EXTRACT PATCHES ETC.
*SIMPLY MORE SPACE ON YOUR MODEM-DISK, IF YOU ARE A DISK USER
2.4. DMSWB
-----
DMSWB is a Workbench based version of DMS. It works just like
DMS but is iconbased.
DMSWB has more advantages, such as being multitasking,
so you can write a DMS file, while you're viewing the information
about it, or you can compress a disk using another drive.
Because DMSWB can do 4 commands at a time, you have 4 information
outputs on the right side of the DMSWB window.
DMSWB has been tested on, Kickstart 1.3 / 2.x / 3.x .
You can use either reqtools.library or asl.library, for
filerequests.
Included on the disk are both asl.library and reqtools.library,
just rename the needed reqtoolsXX.library for use on your
kickstart version, to reqtools.library.
Note, DMSWB is limited in speed and some operations, so
register and get a full version.
Read the REGISTER.ME file for more information.
2.5. File-Masher System (FMS)
------------------------
FMS is a part of DMS, which allows the user to pack files
and include those files to the DMS file.
DMS and FMS, a 2-in-one file packing utility.
FMS is file compressor for data and/or executable not unlike files.
DMS shows that it can compete with LhA in file packing, and combining
both diskimages and files in one single archive, this makes it even
more powerful.
FMS will detect DMS images(tracks) and tell you if found,
and vice versa when unpacking tracks.
When packing whole directories, FMS is very simple to use for this.
Specify directory for packing, and the directory + subdirectories
will be packed without having to do anything, but specifying the
directory.
Chapter 3.
----------
dms v2.03
---------
Bugs in dmswb
-------------
- Dmswb did not deallocate occupied memory when the program
was ended.
- Saving of prefs was disabled, this option is now enabled.
- Processes 2-4 did not write proberly, because their
task-priority was set to -1, their priority is now 0.
Bugs in dms
-----------
- When the ctrl-c option was added, dms did not work with "<nil:" ,
and was waiting for a key-press, ignoring input from "nil".
Updated
-------
Included the installer script, which makes it easier to install dms
and dmswb correctly for use.
Updates in dms
--------------
- Added a "end info" about errors during command execution.
verify errors and read errors.
- Made it possible to create a self-extracting dms file,
using the sfx command which you can read more about
in "dms commands"
- Added a little utility, "undms", which is for unpacking
of dms files only, and is very small(17Kilobytes) in size.
- Added another option called "retry", which is for
reading of bad disks, and for retry of writing with verify.
- Detecting of removed disks while reading/writing!
(have anyone really tried this!?!)
- Changed the type routine to use work out from the size
of the window opened.
so when a full screen page has been typed , you will be prompted
with a "Press Return to continue".
and the ability to press the ctrl-c key while text is being typed.
Updates in dmswb
----------------
- Added a "end info" about found errors during command execution.
verify errors and read errors.
- Detecting of removed disks while reading/writing!
(have anyone really tried this!?!)
- Multiselection included, but for the moment only 2 files
are selectable, and only works with writing of dms files.
- Added selectable viewing of information about unpacked files.
called "show result"
when "show result" flag is on, you will always view the
status about the unpacked file.
when "show result" is off, you will only see this requester
about the unpacked file, when an write-error occured.
3.1 dms V2.02
---------
Bugs
----
- When dms installed a disk, it did not use the disk identity :
ffs/dircache/international.
- File_id.diz description was being packed, so the bbs's utilities
could not extract the file_id.diz correctly.
- Only the registered version of dms v2 could detect read-errors
on source disk, We have changed it to work with evaluation copies.
updated
-------
- It's now possible to break 'dms' when you are requested for a disk.
- FMS file version number have been changed to follow the earliest
version of dms 2.0 , so people knows which 'dms' to use, when
they get a .dms image with files added to it.
- DMSWB is finished and is included in this package.
- Added the file_id.diz extracter/viewer in this version.
3.2 dms V2.01
---------
Bugs
----
- The evaluation copy, was beta-protected against using other drives
than df0:, this is removed.
this version of dms is able to read/write from any drive.
- The evaluation package of dms couldnt be unpacked, on normal 68000
computers (a500/a600 without 680x0 processor).
the self-extracting utility is corrected to unpack
on all computer types.
- The "write" option was seems to crash when trying to write
a track 80(which is the file_id.diz header)
this error is corrected.
- DMS could not be executed from workbench. that part is corrected.
Updated
-------
- DMS.DEVICE had a minor bug in the mountlist supplied with the
documentation.
- We have included an update which is optimized in code and now
%20 the filesize of the original dms.device
- If you register your DMS, you will receive an update which
will enable you to run the dms.device as a virtual drive at
high-speed, which can be compared to a normal diskdrive.
By using a new option in dms, called "DEVFIX", which
enables a "dms.device correct", you will gain this high-speed.
For more information read through the doc "DMSDEVICE.DOC"
- Included the .SFX file make as an option in DMS, so you can
make your own .SFX files, when you have made a .FMS file.
3.3 DMS v2.00
---------
Bugs
----
PROBLEMS WITH WRITING NEW DMS FILES WITH DMS v1.11
- A lot of people couldnt write the new dms files with older versions
of dms (1.11/1.12) due to a bug in the old version, originally they
wanted the dms to detect DOS versions but!, they didnt expect DOS
version to be higher than 1 (DOS boot header is like this: DOS0/DOS1)
but with the OS 3.x ,it is possible to do new formats like CACHE/INT.
So when i updated the infos, the old dms couldnt accept it anymore.
but i moved the infoheader from the old position,so the OLD dms 1.11
can unpack those new DMS files once again.
VERIFY ERROR WHEN WRITING TRK0 ADDED TEXTS
- Some TRK0 adders, did NOT pack a whole trk0, and DMS could not write
only part of tracks, and therefor would a compare of a written track
give you a VERIFY error. But from this version and up, you will not
have this problem.
READ-ERROR REPORTS WAS NOT DISPLAYED WHEN USING ANOTHER DMS VERSION
- When i made this routine, well, i forgot to keep an equeal qualifier
for all READ-ERROR's in all DMS updates, but as i kept on updating
i simply also updated the info in the read error map, so
when DMS 1.53 unpacked a disk packed using DMS 1.51 . DMS v1.53
did not detect those read-errors on found using the DMS 1.51.
this version will detect old read-errors found using DMS 1.51-53
and newer versions.
SIMPLY: DMSWIN REMOVED!
- Firstly, DMSWIN was NEVER really intended updated by me, but
I just included a few options as the verify in it.
But due to the way DMSWIN was made, a lot of people got
only problems using the new version, I might say, that i didnt
do it well.
but from now on, its all gone.
The registered version includes a completely new DMS which
got ALL-IN-ONE. And it will not take up more memory because the
executable file is larger, only diskspace.
but you got the DMS COMMANDLINE version,DMS WINDOW version
in one file. And a preferences can be made so DMS will
only start in commandline mode for those who which to, and
as DMSWIN for WORKBENCH users..
If DMS is started from workbench it will automatically start
the DMS WINDOW version.
UPDATED
-------
- From this version DMS will be able to read PCx: disks,
if they are using the Workbench/Crossdos MS/PCDOS devices.
Both 720K and 1.44 Megabytes disks.
- For easier use of the combined use of HD disks on PC systems and
Amiga computers, I made some changes in the way of reading
High density disks.
Its now two seperate options....
If PC is added to the command line it will read a PC disk using
the PCx: device.
If HD is added to the command line it will read the disk in drive
as a high density disk, either in PC or AmigaDOS format.
AmigaDOS is default.
- The DMS APPEND option have now been modified to work with all
combinations of packing (HEAVY1/HEAVY2/NONE)
- DMS is using "if possible" the SHI VIRUS bootblock library, for
detecting viruses in the bootblock.
Read for more information the files included in the directory
about SAFE HEX INT.
you can find the latest bootblock.library, in this directory too.
> DIRECTORY NAME: SHI-TOOLS
>HOW TO USE IT:
>~~~~~~~~~~~~~~
>Well, for you, the user, it's really very simple!
>
>Just install the Bootblock.library in your LIBS: directory, and
>install the Bootblock.brainfile in your L: directory!
>
>There, that wasn't so hard, was it? 8-)
>
>Now the library/brainfile are ready for use by any program that
>supports them!
>
>Happy virus-hunting!
******************************************************************
* A NOTATION TO FUTURE UPDATES OF THIS UTILITY: Bootblock.library*
* It is not legal (by law of Commodore), *
* to use uppercase letters in the library name. *
* I had several problems with opening this library because of *
* this , and I think others have the same problem. *
******************************************************************
* ALWAYS USE lower-case LETTERS IN THE LIBRARY NAME RECOGNITION. *
******************************************************************
- the REPACK option was first of all not working at all, in the
way it should. It would take a maximum of 80 packed tracks
whatever it was 80 tracks consisting of trk0's and so on.
It is now changed and it is also possible to use the NOTEXT
option here, so text adds will be skipped when repacking.
And all appended tracks will be transfered to the new dms
archive.
- Added a "FILE_ID.DIZ" option, named DIZTEXT, which allow you
to add a BBS information text to the .DMS file.
- ALL NEW UPDATES OF DMS WILL BE RELEASED AS A .RUN (SELF-EXTRACTING)
FILE. SO ONLY THESE FILES ARE VALID UPDATE VERSIONS.
3.4 DMS v1.53
---------
BUGS
----
- When DMS reported VERIFY ERRORS the program just said track 0 even on
other tracks than 0....
- The same goes for the READ-ERROR routine, but it is repaired now..
the fill routine for the READ-ERROR was also incorrect, that is fixed
- I have 2 times forgotten to include the INSTBOOT program for the
DMSTEST program, this is now included in the archive...
- The DMSTEST Program included in previous packages, was only a
680x0 version.. i have now placed 2 version, one 68000 and an 680x0.
3.5 DMS v1.52
---------
READ ERROR detection
--------------------
BUGS
----
- DMS did not report is a BAD track was read, and that is now fixed
so when packing/unpacking the track, you will be notified about the
bad track.
UPDATED
-------
- Bootblock installer for Virus infected disks..
Normally the Bootblock detecter would install the infected disk
with a Kickstart 1.3 bootblock, but this version installs your
infected disk with an updated installed Bootblock (Kickstart 2.x/3.x).
- More exact viewing information about the .dms file to be unpacked,
which Kickstart version needed to use this disk..
FileSystem info..e.t.c..
Chapter 4.
----------
Register information.
---------------------
You can register your version of the Device-Masher System
by filling out the registration text included with the package.
It costs Dkr 200, to register DMS.
Send only CASH or International Money Order(From your postoffice)
And by being a registered user, you will receive the latest updates
of Device-Masher System(DMS), and other utilities made by Parcon.
Register form and suggestions/bug reports can be sent to:
ParCon software.
v. Michael Pendec
Islandsh0jparken 5, st.th.
DK-2990 NIVAA
DENMARK
We have received several letters, concerning registration. Often asked,
were "Can I pay in Danish Kr", We want you to send the fee in Danish Kr,
and if its impossible for you to do, then go to your local postoffice,
and send us a International money order, shipped by the postoffice.
If you decide to include cash in your letter, include ONLY DANISH Kr 200,
Or US DOLLARS $30. We will NOT ship DMS out on "C.O.D [Cash On Delivery]"
nor payment after receiving DMS.
There is only ONE WAY to get DMS, include money with your register form,
or use the International Money order, made at your local postoffice.
Chapter 5.
----------
You can reach us on this bbs, leave mail for : Michael Pendec
I do not, at this time, have a FIDO-NET MAIL ADDRESS, so
a reply to your mail is not possible, but all requests,
bugreports will be looked into.
FIDONET:
Perto's AssholeBBS +45-86720273 16k8 DUAL 2.xGb 2:230/815
Perto's AssholeBBS +45-86720274 14k4 HST 2.xGb 2:230/816
Perto's AssholeBBS +45-86293910 14k4 V32b 2.xGb 2:230/817
Perto's AssholeBBS +45-87370010 64k0 ISDN 2.xGb 2:230/1815